Click any tag below to further narrow down your results
Links
Anthropic built Scion, a custom version control system, to replace Git because Claude's code generation capability pushed their merge rate from 2,500 to 30,000+ code changes per day—a scale Git's distributed design couldn't handle. The system treats clients as always-online agents and moves computation to the server, ditching Git's model of complete local repositories.
- Anthropic's monorepo became unmanageable under Git: the history alone is 100 GB, and they were doing 25 million checkouts daily for CI, which would generate 600 PB of traffic if done naively.
- Scion's core design flips Git's assumptions: clients stay thin and online, the server handles all history queries and merges, and there's no single fully-materialized copy of the repo anywhere—everything is distributed and horizontally scalable.
- The system uses "changesets" (write-ahead log entries) instead of Git commits, storing only what changed relative to the parent plus content-addressed pointers to blob storage, allowing high-throughput acceptance with no packfiles or cross-server locking needed.
Anthropic released a two-hour course led by the engineer behind Claude Code that walks you through building self-managing Claude agents. It covers terminal integration, file-system memory, hallucination-blocking hooks, and scaling to large codebases. Whether you’re a beginner or advanced user, you’ll finish ready to use Claude professionally.
- Anthropic released a free two-hour course on building Claude agents, led by the engineer who writes Claude Code
- Covers terminal integration, file-system-based memory, and hooks designed to catch and block hallucinations
- Includes guidance on scaling agents to large codebases via isolated environments and multi-file task orchestration
- Shows real failure examples (missing dependencies, misread logs) and how to harden pipelines against them
Boris and Cat, the team behind Claude Code, explain how a terminal tool grew out of an internal prototype after an engineer was told to use it instead of hand-writing code. They cover why giving the model bash and a few tools worked better than building a custom toolkit.
- Claude Code began as an internal research tool called Clyde. A new engineer's hand-written PR got rejected with "use Clyde," and the one-shot result convinced the team that an IDE might not be necessary.
- The turning point was giving the model bash. It started writing AppleScript and automating things on its own, which the team had not expected.
- Anthropic "dogfoods" the product: roughly 70 to 80 percent of technical staff use it daily, and internal feedback arrives constantly, so features get shipped or pulled within days.
- The team has been removing tools over time. The LS tool was dropped once bash permissions could enforce directory restrictions, which leaves less clutter in the model's context.